docs: explain addon version differences - #8868
Merged
gustavodiaz7722 merged 1 commit intoSep 18, 2026
Merged
gustavodiaz7722 merged 1 commit into
gustavodiaz7722 merged 1 commit into
Conversation
Signed-off-by: Atharva Joshi <josh.atharva2005@gmail.com>
Contributor
|
Hello atharvaHJoshi 👋 Thank you for opening a Pull Request in |
gustavodiaz7722
approved these changes
Sep 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #7864
What this PR does
Users compared the version applied by
eksctl utils update-aws-node/update-kube-proxy/update-corednsagainst the list fromeksctl utils describe-addon-versionsand saw mismatches. This is by design, but thedocs did not explain it.
Changes
Adds a "What 'latest' means for each command" section to the default add-on update
guide that clarifies:
describe-addon-versionslists EKS Managed Add-on versions (their own releasecadence and
-eksbuild.xsuffix).update-aws-node/update-corednsapply the manifest bundled with the eksctlrelease ("known good" version), not the newest EKS-managed version.
update-kube-proxyresolves the newest version for the cluster's control-planeversion from the EKS API.
add-ons via
eksctl create addon/eksctl update addon --version latest).